If you did a Custom install and put any instances of iMISpublic (see Choosing single or multiple appservers) on different appservers from iMIS, you need to edit their web.config files (each instance has its own) to point to iMIS. This is needed to ensure proper logon handling. You also need to open ports through your firewall, if one stands between appservers.
To specify an iMIS instance for logon handling
1. Open the web.config file for editing.
Default location: C:\Program Files\ASI\iMIS\iMIS_public
2. Locate the <appSettings> element.
3. Within the <appSettings> element, locate the ImisWebServerUrl key.
<add key="ImisWebServerUrl" value="http://appserver/iMIS" />
4. Modify the value attribute to ensure that it points to a valid URL for an instance of the iMIS application that uses the same iMIS database as this instance of the iMISpublic application.
Caution! If you have multiple iMIS databases (such as test and production), be careful to specify the location of an iMIS application that uses the same database as this instance of the iMISpublic application. This is critical because all user records are stored in the iMIS database.
To open communication between appservers
1. If a firewall stands between two appservers, configure it to allow traffic between them through port 80 (HTTP), port 443 (HTTPS), and 1433 (SQL default).
2. Test that the appserver on which iMISpublic resides can communicate with the designated appserver for iMIS and the iMIS database server.
To tunnel communication
If you do not want to open port 80 (HTTP), port 443 (HTTPS), and 1433 (SQL default) through your firewall, you can have the remote iMISPublic appserver use a VPN tunnel for network connections to the appserver for iMIS and the database server.